Skip to content

ci: update GitHub Actions to latest versions - #190

Closed
Project516 wants to merge 1 commit into
openai:mainfrom
Project516:ci/update-github-actions
Closed

ci: update GitHub Actions to latest versions#190
Project516 wants to merge 1 commit into
openai:mainfrom
Project516:ci/update-github-actions

Conversation

@Project516

Copy link
Copy Markdown

Summary

Surveyed open and closed PRs in this repo: no existing PR updates the GitHub Actions to their latest released versions (the most recent CI work, #163, #91, #84, #10, touched workflow logic, not action versions).

Updates all SHA-pinned actions to their latest stable tags:

Action From To
actions/checkout de0fac2e… # v6.0.2 3d3c42e5… # v7.0.1
actions/setup-node 53b83947… # v6 82076278… # v7.0.0
SocketDev/action 937f824e… # v1 ba6de6cc… # v1.3.2
oven-sh/setup-bun comment only # v2.2.0 (pinned commit already v2.2.0)

Unchanged (already at latest): docker/setup-buildx-action v4.2.0, docker/build-push-action v7.3.0, docker/login-action v4.6.0, pnpm/action-setup v6.0.9, actions/upload-artifact v7.0.1, actions/download-artifact v8.0.1, actions/attest-build-provenance v4.1.1.

No breaking input changes: checkout v7 drops no inputs used here and adds fork-PR safety for pull_request_target/workflow_run; setup-node v7 migrates to ESM and keeps node-version/cache/registry-url/package-manager-cache support.

Verification

  • All 6 workflow YAML files parse cleanly.
  • No stale pinned SHAs remain.
  • Changes are limited to uses: pins and version comments.

- actions/checkout v6.0.2 -> v7.0.1 (SHA-pinned)
- actions/setup-node v6 -> v7.0.0 (SHA-pinned)
- SocketDev/action v1 -> v1.3.2 (SHA-pinned)
- oven-sh/setup-bun comment corrected to v2.2.0 (commit already current)
@mldangelo-oai

Copy link
Copy Markdown
Collaborator

Thank you for checking the versions of our GitHub Actions. We do not currently have a failure or security issue that calls for changing these protected release workflows, and some of the proposed pin changes do not alter the action's runtime behavior. Given the risk of changing publication paths without a specific need, I'm going to close this one. We'd be happy to consider a smaller update tied to a particular bug or security advisory.

@Project516
Project516 deleted the ci/update-github-actions branch August 1, 2026 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants